Inventory control and prescription dispensing system

ABSTRACT

A prescription dispensing system including a dispensing vault for storing for storing and dispensing prescriptions, with the vault further including RFID, bar code, and other means for verifying the content and internal location of pre-filled prescriptions; a customer interface that uses customer biometrics to ID a customer to ensure that prescriptions are only dispensed to the correct person; a patient registration system in communication with the central computer system for collecting insurance, doctor, biometric, and other information to facilitate transactions; transport container that integrates into the dispensing vault and provides secure transportation from a pharmaceutical manufacturer to the dispensing vault.

PRIORITY OF INVENTION

This is a divisional of prior application Ser. No. 11/507,093, andclaims priority of invention under 35 USC 119(e) from U.S. ProvisionalPatent Application 60/709,645 filed Aug. 19, 2005.

TECHNICAL FIELD

The present invention concerns inventory control systems and dispensingsystems for, in particular, prescription drugs.

BACKGROUND OF THE INVENTION

The number of prescriptions filled each year by pharmacies in the UnitedStates is fast increasing. This puts additional demands on pharmaciesand pharmacists to fill prescriptions in a timely manner. Many peoplehave experienced the frustration of a long wait at a pharmacy simply tohave a common prescription filled or refilled.

There are numerous problems with the present system used for thedispensing of prescription medicines. First, current practices rely uponthe memory of the prescription provider as to the pharmaceutical to beprescribed. This introduces a series of potential errors. Second, mostprescriptions are produced without the aid of checking against a knowndatabase of allegories and interactions. Third, it primarily relies uponhand-written scripts that must be translated by a pharmacist. Thisinjects a first level of translation error into the process, and oftenrequires a pharmacist to verify a prescription with the prescribingdoctor. This adds additional time and delay to the prescription fillingprocess. Fourth, it requires patients to obtain scripts from theirdoctors and then travel to their pharmacy to have the prescriptionfilled. Once at the pharmacy, patients may be subjected to delays andhuman error caused by pharmacists rushing to meet the accumulateddemand.

Various attempts have been made to automate the dispensing ofprescription drugs to address these issues. However, these attemptssuffer from one or more of the following shortcomings. First, a criticalconcern in any remote dispensing situation (i.e., one where thedispensing is not under the direct control of a pharmacist) is that onlyan authorized person receive the medication and that the correspondingmethod of authorization should not be readily forged or compromised.Thus, a secure method of patient identification is required. These knownsystems typically generate a code at the time a prescription isgenerated. This code is then entered into a remote dispensing apparatusby a person desiring to obtain a prescription. However, this code iseasily transferred to, or otherwise obtained by, persons who are notauthorized to obtain the prescription. Further, most patients willrecord the code on a document rather than risk forgetting the code. Thisprovides another mechanism by which an authorization code can beobtained by an unauthorized user. Thus, these known systems lack such asecure method of patient identification and introduce multiple pointsfor such a code to be lost or otherwise compromised.

Second, because a pharmacist need not be present in remote dispensingsituations, a remote dispenser must include multiple, redundantverifications to ensure that the prescribed medication, and only theprescribed medication is, in fact, dispensed. Known remote dispensingsystems typically employ a single level of verification that istypically comprised of a barcode scan of a barcode that was applied by arepackaging pharmacy prior to loading of the product into inventory ofthe remote dispenser. If a product is mislabeled at the repackagingpharmacy, a single level of verification will not determine that theproduct is mislabeled, greatly increasing the possibility that anincorrect product is dispensed. Likewise, if a product package isimproperly filled (quantity too high or too low), these known systemshave no ability to determine this condition. Thus, there is a need for aremote dispensing system that provides multiple, redundant verificationsto ensure that only the correct prescription is dispensed.

Third, the present systems lack coordination between the upstreampharmaceutical suppliers and the remote dispensing devices, such that anexcessive amount of time and labor is required to restock the dispenserand verify that stocked drugs have not reached an expiration date, orhave otherwise had their quality compromised (e.g., through atemperature transient).

Fourth, the present systems lack a secure method of transferringprescription medications from a repackaging pharmacy to a remotedispensing device and from a remote dispensing device to repackagingpharmacies.

Fifth, the known systems do not provide for a high density of productstorage and the ability to randomly access any product contained in theinventory of the remote dispensing device. As a result, the frequency ofneed for human interaction to restock a remote dispenser is increased.Further, this lack of random access significantly limits the number ofdifferent products that can be stocked in a remote dispenser.

Accordingly, there is a need for an inventory control and prescriptiondispensing system that quickly and efficiently delivers prescriptiondrugs to patients in locations where a pharmacist is not necessarilyphysically present, that minimizes the potential for translation errorsbetween a prescriber and a pharmacist, that provides adequate securitythat prescription drugs are only dispensed to authorized persons, thatprovides multiple, redundant systems to ensure that correct prescriptiondrugs are dispensed, that coordinates the restocking and quality controlof prescription drugs available within the remote dispenser, thatprovides for a secure method of transporting prescription medicationsbetween a repackaging pharmacy and a remote dispensing device, and thatprovides for high density product storage and random access to productsstored.

SUMMARY OF THE INVENTION

To address these needs, the inventor has devised a new system and methodfor prescribing, dispensing, managing inventory, and ensuring theintegrity and security of dispensed medications. One embodiment consistsof a dispensing system that is self contained and stores a variety ofcommonly filled prescription drugs. This dispensing system is incommunication with prescribing providers, insurance companies, banks andcredit card companies, pharmacist, pharmacy business management systems,point of sale systems, repackaging pharmacies, and patients. This systemallows for the remote dispensing of prescription medications, whilemaintaining the security and integrity of the medications, maintainingcontrol over to whom products are dispensed, allowing for communicationsbetween the patient and a remote or local pharmacist, and facilitatinginsurance and financial transactions. The system further provides forincreased storage density and random access capabilities that allow anyindividual product within the remote dispenser to be accessed at anytime.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an embodiment of the present invention.

FIG. 2 is a side view of an embodiment of the robotic arm system of thepresent invention.

FIG. 3 is a front isometric view of an embodiment of the remotedispenser of the present invention.

FIG. 4 is a front isometric view of the interior of an embodiment of theremote dispenser of the present invention.

FIG. 5 is a plan view of an embodiment of the rotating shelve of thepresent invention.

FIG. 5A is an isometric view of an embodiment of the rotating shelve ofthe present invention.

FIG. 6 is an isometric view of an embodiment of the rotating shelve ofthe present invention.

FIG. 7 is an isometric view of the loading system of an embodiment ofthe present invention.

FIG. 8 is an isometric view of an embodiment of the grabber assembly ofthe present invention.

FIG. 9 is an side view of an embodiment of the loading door lockingsystem of the present invention.

FIG. 10 is a plan view of an embodiment of the transport container lidof the present invention.

FIG. 11 is a plan view of an embodiment of the transport container baseof the present invention.

FIG. 12 is an isometrice view of an embodiment of the transportcontainer of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following detailed description, which references and incorporatesthe Figures, describes and illustrates one or more specific embodimentsof the invention. These embodiments are offered not to limit but only toexemplify and teach the invention, and are shown and described insufficient detail to enable those skilled in the art to practice theinvention. Thus, where appropriate to avoid obscuring the invention, thedescription may omit certain information known to those skilled in theart.

The inventory control and prescription management and dispensing systemof the present invention provides for the safe, secure, and convenientdispensing of prescription medications in a variety of non-traditionalsettings, while providing safeguards to ensure that the propermedication is dispensed to the proper person, and that the quality andefficacy of the medication has been preserved and maintained. Itprovides a secure system for transferring prescription medicationsbetween repackaging pharmacies and remote dispensing devices. It furtherprovides the flexibility to accommodate a variety of transaction typesand permutations.

System Overview

Referring to FIG. 1, a block diagram of the inventory control andprescription dispensing system is shown. This system includes thePatient Registration System (PRS) 10, the Prescription Writing System(PWS) 11, the Remote Dispensing System (RDS) 12, the Central Server 13,the Financial Transaction System (FTS) 14, the Pharmacy Billing ManagerSystem (PBMS) 15, associated Insurers 16, Repackaging Pharmacy 17,Transport Carton 18, and pharmacists 19. A communications network allowsfor communications between the various components. Proprietary softwarecontrols security and permissions for communications, and access tostored data throughout the system.

Patient Registration System (PRS)

PRS 10 is the point at which essential patient information necessary tofacilitate the use of RDS 12 is captured. This information includes thepatient's personal data, including name, date of birth, demographicinformation, insurance information, financial (bank and/or credit cardinformation) and physician name. A patient's medical history includingallergies, problem lists, current prescriptions and the like, are alsocaptured. Biometric information is collected by the PRS and may includefingerprint, iris scan, voice scan, photographic scan, or otherbiometric information that is unique to a particular patient. Thisbiometric information provides a unique identifier for each patient andis used to verify patient identity at RDS 12. Information that iscollected through PRS 10 may be stored on a local RDS 12 and/or storedon central server 13. PRS 10, via a communications network, communicatesprimarily with RDS 12, other registration systems, prescription writingsystem 11, and central server 13.

Prescription Writing System

PWS 11 allows a prescription provider to generate either an electronicor paper based script. PWS 11 includes a handheld computer (commonlyreferred to as a PDA) that is networked to RDS 12, typically through aserver located in the provider's office. This communication may beeither through a wired network or a wireless network. Proprietarysoftware is used to handle data transfer and communications between PWS11 and RDS 12, central server 13, and PRS 10. As a first step, patientspecific information, such as demographics, insurance information,medical history, problem list, allergies, and current medications thatis collected by PRS 10 is transmitted to the PWS 11. RDS 12 transmits acurrent inventory of products (a formulary) to PWS 11. Following apatient encounter, a prescription provider desiring to write aprescription, enters the prescription into the PDA. The proprietary PWSsoftware then performs a drug utilization review, which includesdrug-drug interaction, dosage range checking, patient allergy checking,pregnancy and lactation alerts, and other safety checks. The PWSsoftware, through PBMS 15, also determines whether the prescribedmedication is covered by the patient's insurance 16 and is available atRDS 12.

Any RDS 12 on the network can be queried to determine the availabilityof the prescribed medication. If the prescribed medication is notavailable through an RDS 12, or if the patient would prefer a paperbased prescription, a paper based script can be generated through PWS11. Otherwise, an electronic prescription is transmitted by PWS 11 to aRDS 12 that is specified by the patient or is transferred to atraditional pharmacy as an electronic prescription or by facsimile.

Remote Dispensing System

Vault System

Referring to FIG. 3, a front isometric view of RDS 12 is shown. RDS 12consists of vault 100 in which products (not shown) are stored fordispensing. Vault door 112 is hingedly connected to vault 100 by hinges101 and is secured in a closed position by lock 116. Positioned on orthrough vault door 112 are light 102 which provides illumination for thefront of vault 100, camera 111, which captures a video record oftransactions, video monitor 104 which provides user feedback, keyboard107 for user data input, dispensing slot 106, through which product isdelivered to users, pick-up sensor 105, which provides a signal whendispensed product is removed from dispensing slot 106, insurance cardreader 108, which creates a bitmap image of a user's insurance card,loading door 109, through which product is introduced into vault 100inventory, wireless antennae 110, for wireless communications, biometricreader 114, for capturing a user's biometric identification information,magnetic card reader 115 for capturing information contained on magneticstrips, such as credit cards, prescription reader 117, for creatingbitmap images of paper scripts, printer 121, for printing receipts andproduct safety information, RFID sensor 118, for receivingcommunications from a transport carton (not shown) being placed intoinventory, castors 129, for movement of vault 100, and tilt securitydevice and sensor 120 for preventing movement of vault 100 anddetermining if vault 100 is being shaken, overturned, or otherwisedisturbed.

Referring to FIG. 4, a front isometric view of RDS 12 is shown withvault door 112 in the open position. Security bar 206 provides aphysical barrier between the lower portion of vault 100, where productis received through loading door 109 for placement into inventory, andthe upper portion of vault 100 where product is stored for dispensing.Alternatively, security bar 206 may be formed as a plate that extendshorizontally from the front of vault 100 to the rear of vault 100.Positioned in the base of vault 100 are battery backup 201, motorcontroller 202, refrigeration unit 203, communications module 204, andCPU 205 which also provides a memory for data storage. Shelf axel 904extends vertically from the base of vault 100 to the top of vault 100.Rotating shelves 602 are rotatable about shelf axel 904 and are stackedvertically within vault 100.

Shelve System

As shown in FIGS. 4, 5, and 5A, in this embodiment rotating shelve 602is substantially circular and may be formed from sheet metal or moldedfrom a suitable plastic material. Shelve lip 608 defines the outerperiphery of rotating shelve 602. Access slot 603 extends from centralbore 606 to the periphery of rotating shelf 602.

Shelf lip 608 extends parallel to the axis of rotation of rotatingshelve 602 from the periphery of rotating shelf 602, including theperiphery created by access slot 603, and creates an axially extendingshoulder which, in conjunction with shelf floor 607 defines a receivingspace for storing product. Bottle holder insert 902 is positioned withinthis receiving space and includes a plurality of circular voids that aresized to accommodate standard sized prescription medicine containers.

Rotation of rotating shelves 602 is performed by drive system 903. Drivesystem 903 consists of shelf drive motor 905, pulley 906, and drive belt907. Each rotating shelve 602 is rotated by an individual drive system903 (not shown for clarity). The distance between drive motor 905 andpulley 906 is slightly wider than the width of slot 603 so that rotationof rotating shelves 602 is effected even when drive motor 905 or pulley906 is aligned with slot 603. Rotation of drive belt 907 results in acorresponding rotation of rotating shelf 602 about an axis defined byshelf axel 904. In one embodiment of the system rotating shelves 602have surface mounted encoding strips 604 positioned along the outsidesurface of shelve lip 605. These encoding strips 604 are read by anencoder that is integrated into drive system 903 to allow thecontrolling software to detect and adjust the exact rotational positionof each rotating shelve 602. Alternatively, or in conjunction with thismethod, an optical or magnetic encoder may be placed on each drivesystem 903 in order to detect rotating shelve 602 rotational position oradjust rotating shelve 602 rotational position. These forms of encoderstypically allow for rotational position determination within an accuracyof hundredths of a millimeter.

In an alternative embodiment, shelves 602 are square or rectangular anddo not rotate. In this embodiment, shelves 602 are supported from theperimeter of shelves 602 by engaging adjustable racks located withinvault 100.

Robotic Arm System

Referring to FIG. 2, robotic arm system 400 is shown. Robotic arm system400 is located interior to vault 100 and extends vertically from thebase of vault 100 to the top of vault 100 and is positioned to beproximate to the periphery of rotating shelves 602. Robotic arm system400 is capable of vertical, horizontal, and depth movement. Vertical arm415 extends between head support 416 which is attached to the interiorceiling of the vault and base support 401 which is secured to the floorof vault 100. Because of the need for security in this application allmounting hardware for the vertical axis is secured internally withoutobviously removable supports. Proximate to vertical arm 415, and alsoextending vertically between head support 416 and base support 401 isvertical lift screw 403. Vertical carriage 404 rides along vertical arm415 and is driven vertically (Y-Axis) by vertical lift screw 403. Thisis accomplished by a engagement system commonly referred to as a ballscrew or lead screw. In this embodiment of robotic arm system 400 thelift screw 403 moves through a threaded block attached to the verticalcarriage 404. During rotational movement of lift screw 403 therotationally fixed block is forced upward or downward according to therotational direction of lift screw 403. Vertical drive system 405includes a motor, gearbox, and position encoder, and provides the motiveforce to turn vertical lift screw 403 to effect movement of verticalcarriage 404. The included encoder utilizes a magnetic or opticalpick-up to count fractions of revolutions of vertical lift screw 403,from which the vertical position (Y-Axis) of vertical carriage 404 isdetermined. Limit switches 402 limit the travel of vertical carriage 404in both upward and downward directions in a known manner and allow forfurther calibration and control of the system.

Horizontal drive system 416 includes a motor, gearbox, and positionencoder, and provides the motive force to turn horizontal drive screw417 to effect horizontal movement of grabber assembly 1100. Referring toFIG. 4, the width of vault 100 is defined to correspond to the X-axis,the depth is defined to correspond to the Z-axis, and the height isdefined to correspond to the Y-axis. Grabber assembly 1100 moves alongthe length of horizontal arm 414 in a plane defined by the X and Z axes.The included encoder utilizes an optical or magnetic pick-up to countfractions of revolutions of horizontal drive screw 414, from which theposition (location) of grabber assembly 1100 is determined with respectto the X and Z axes. Total travel of grabber assembly 1100 is limited,in a known manner, by limit switches 402, positioned proximate to eachend of horizontal arm 414. In one embodiment, vacuum to grabber assembly1100 is provided by vacuum pump 418 through vacuum line 406. Vacuum iscontrolled by suction sensor 409 and suction control solenoid 408. Inanother embodiment, suction and suction control are provided on grabberassembly 1100.

Referring to FIG. 8, grabber assembly 1100 is shown. Grabber assembly1100 is composed of rotational motor 410, video/still camera 411,grabber/suction fitting 412, vertical position sensor 413, vacuum 419,optical encoder 420 and bracket 421. Bracket 421 is L-shaped with thevertical portion engaging horizontal arm 414 in a manner that allows forlimited, damped vertical movement of bracket 421 with respect tohorizontal arm 414. Grabber suction 412 is positioned below thehorizontal portion of bracket 421 and is rotatable about an axis definedby shaft 418. In this embodiment, suction is supplied to grabber suction412 by vacuum pump 419. Rotative motor 410 provides the motive force torotate grabber suction 412. Optical encoder 420 determines therotational position of shaft 418. Vertical position sensor 413 is usedto determine the vertical (y-axis) position of grabber suction 412.Grabber video 411 provides a video image of the position and location ofgrabber assembly 1100 and a video image of product captured by grabbersuction 412.

The combination of linear movement of grabber assembly 1100 androtational movement of rotating shelves 602 provides complete randomaccess capabilities to all product stored in the RDS vault. This allowsfor both high density storage and a wide product mix when compared toprior art systems.

Communications and Controls

The RDS utilizes an internal computer (processor, data storage,communications) 205 to manage and control the loading, inventorying, anddispensing of product. As shown in FIG. 1, the RDS 12 is also incommunication with prescribing providers (through prescription writingsystem 11), patient registration system 10, repackaging pharmacies 17,pharmacy business management companies 15, insurance companies 16,financial institutions 14, and participating pharmacists 19. Thesecommunications are either internet based using secure internet protocolsor local using proprietary or standard protocols and may be effectedeither through wired, or wireless, connections.

Several software applications are resident on the RDS computer 205.These applications control the receipt, loading, and verification ofproduct placed into the RDS vault 100; management of inventory in theRDS vault 100; internal operations associated with the selection,retrieval, inventory and dispensing of product; product verificationprior to dispensing; product labeling prior to dispensing; databasefunctions; communications between the RDS and prescribing providers,patient registration systems, repackaging pharmacies, insurancecompanies, and banks and credit card companies; security andsurveillance; patient identification; paper prescription reading;insurance card reading, product instruction printing; user interfaces.

Transport Carton System

Referring to FIG. 12, transport carton 1007 is shown. Transport carton1007 is used to securely transfer prescription medications to and from arepackaging pharmacy. In the embodiment shown, transport carton 1007 hasan arcuate outer edge, spanning an arc of approximately 90 degrees, andtwo, perpendicular inner edges, extending linearly from each end of thearc. In this embodiment, transport carton 1007 is essentially shapedlike a slice of pie that forms a 90 degree wedge. Transport carton lid1009 is removably attachable to transport carton base 1013. Data/powerport 1004 and shipping label 1008 are recessed into transport carton lid1009. Alignment guide 1502 facilitates alignment of transport carton1007 in vault 100. Data port 1004 includes a plurality of configurablecontacts through which data is communicated and power is supplied.Transport carton 1007 is preferably fabricated from aluminum, structuralplastic, or other similar material.

Referring to FIG. 10, an underside view of transport carton lid 1009 isshown. In this embodiment, locking mechanism 1402 includes a circularlock ring 1407, which is rotatable about lock axis 1406 and is driven bydrive motor 1404. Four lock arms 1408 are pivotally attached to lockring 1407 and equally spaced about the inner circumference of lock ring1407. Lock guides 1401 are attached to the underside of transport cartonlid 1009 and include a through bore for slidingly receiving the distalend of each lock arm 1408. Clockwise rotation of lock ring 1407 by drivemotor 1404 extends each lock arm 1408 and engages the distal end of eachlock arm 1408 with lock arm receiver 1501 (not shown) which is attachedto transport carton base 1013. Reversing drive motor 1404 results incounter clockwise rotation of lock ring 1407 and the withdrawal of lockarms 1408 from sliding lock receivers 1501. Shipping label actuator 1405is attached at a first end to lock ring 1407 and at a second end toslide 1409. Rotation of lock ring 1407 causes slide 1409 to move from afirst position, where a first address is displayed on shipping label1008, to a second position, where a second address is displayed onshipping label 1008. Electronic lock sensor 1403 determines andcommunicates the lock/unlock status of transport carton lid 1009.

Referring to FIG. 11, a top view of transport carton base 1013 is shown.Sliding lock receivers 1501 extend from and are spaced around theperiphery of transport carton base 1013. Sliding lock receivers 1501 arepositioned to receive lock arms 1408 (not shown). Side walls of base1013 create a volume into which bottles of product 1204 are stored.

In this embodiment, data/power port 1004 contains nine configurablecontact points. These contact points are randomly configurable foreither power or data functionality. Transport carton 1007 furtherincludes an RFID tag (not shown). This tag is affixed at the repackagingpharmacy and programmed with a unique serial number. When a transportcarton 1007 is placed in proximity to an RDS 12 prior to loading intothe RDS, RFID reader 118 queries the transport carton 1007 for thisunique serial number. The RDS then compares the received serial numberto its database to determine if that particularly transport carton 1007is expected and authorized for loading into vault 100 inventory. If thisverification is not successfully completed, loading into the RDS isprevented.

Transport carton 1007 also includes internal sensors (not shown) thatmeasure and record environmental conditions (temperature and humidity)and physical conditions (container orientation and acceleration). Thesesensors input data to a microprocessor and memory which communicate withthe RDS through power/data port 1004. Additionally, the open/closehistory and status of transport carton 1007 and the transit time arerecorded and communicated to the RDS.

Referring to FIG. 9, the locking mechanism for loading door 109 isshown. Loading door 109 is positioned interior to vault 100, proximateto vault door 112. Loading door 109 is supported by door guides 1301which are channel shaped rails in which loading door 109 slides andwhich are attached to vault door 112. Movement of loading door 109 iseffected by motor 1201 which drives drive wheel 1302 which frictionallyengages loading door 109 and causes it to slide in guide rails 1301.Loading door lock 1202 is attached to support 1305 and consists ofsolenoid 1304 and lock pin 1303. Energizing/de-energizing solenoid 1304causes lock pin 1303 to extend/retract. Loading door 109 furtherincludes a bore for receiving lock pin 1303 when lock pin 1303 is in itsextended, or locked, position. Loading door 109 is equipped withposition sensing hardware and software which includes limit sensors,amperage detection, optical sensors and in some embodiments encoders.

Vault Loading and Inventory Control System

A proprietary software application running on RDS computer 205 controlsthe loading of product 1204 from a transport carton 1007 to vault 100storage area. Storage is provided via a high density design that allowsfor maximum utilization of available storage space. In one embodiment,as seen in FIG. 4, a plurality of rotating shelves 602 are stackedvertically about a central support and axel 908. Each tray has an accessslot 603 that runs from the circumference of the tray to the centralaxis of the tray and that is sufficiently wide to allow movement ofhorizontal arm 414 and grabber carriage 1100 within slot 603. Slots 603are vertically alignable so that horizontal arm 414 may be raisedcompletely through the entire stack of trays. In this embodiment, thegrabber assembly 1100 travels linearly between vertical arm 415 andshelve axel 904. Rotation of a shelve 602 under grabber assembly 1100allows all storage locations on each shelve 602 to be accessible bygrabber assembly 1100. In another embodiment, square or rectangulartrays are utilized in conjunction with an elevator system that movestrays as necessary to allow access, between the trays, for the roboticarm system.

Referring to FIG. 7, product 1204 receiving and unloading is shown.Transport carton 1007 has been loaded into product receiving tray 1015through loading door 109 (not shown). Transport carton lid 1009 is shownafter being unlocked and removed from transport carton base 1013 by lidlifting system 1010 and with product receiving tray 1015 rotated 180degrees. Lid lifting system 1010 includes arm 1014, lid lifting motor1001, data/power cable 1002, vacuum supply line 1003, data/power contact1004, and suction cups 1011. Upon loading of a transport carton 1007into vault 100, lifting motor 1001 positions lid lifting system 1010 toengage lid 1009. Data/power contact 1040 engages data port 1004 on lid1009. Data related to the content of the transport carton 1007, andenvironmental parameters to which the transport carton 1007 has beenexposed during shipment are downloaded to CPU 205 and verified andquality checked. If all checks are successful, transport carton lockingmechanism 1402 (not shown) is provided power and lock arms 1408 (notshown) are moved to their unlocked position. Vacuum line 1003 thensupplies a vacuum to suction cups 1011 and lift lifting motor 1001 liftstransport carton lid 1009 to the position shown. Drive system 903 isthen engaged to rotate product receiving tray 1015 into unloadingposition under robotic arm system 400. If one or more quality checks areout of tolerance, no product loading occurs and the RDS transmits anappropriate message to the repackaging pharmacy.

During the unloading process, each individual product container isremoved from the transport carton 1007 by the robotic arm system 400.Each product container is lifted from the transport carton by thegrabber assembly suction cup 412. Each individual product container isshipped from repackaging pharmacy 17 with a bar code label thatidentifies the content of the container and may also include an RFID tagthat provides a second identification of container contents.

The product container's label and RFID tag are then read with a bar codescanner and RFID system (not shown) to determine the contents of thecontainer and the pedigree, e.g., the manufacturer, repackager, lotnumber, expiration date, of the product within the container and storedin memory. In addition other forms of product identification may be usedincluding but not limited to height, width, shape and weight. The RDScomputer 205 directs the robot arm assembly to move the container to aspecified location on a rotating shelve 602 in the vault 100. Eachrotating shelve has a plurality of receiving locations, each defined byspecific Cartesian (x-y-z) coordinates. For example, if the RDS computer205 directs that a bottle of product 1204 be placed in the lowermostrotating shelve 602, robotic arm system 400 moves the bottle verticallyuntil the bottle is at a y-coordinate (vertical) position just abovethat rotating shelve 602. Drive system 903 for that rotating shelve 602then rotates the shelf to the specified rotational position. Robotic armsystem 400 then moves the bottle horizontally to the specified positionin the x-y plane. Once the bottle is positioned in the specifiedposition, and the rotating shelve 602 is in the specified rotationalposition, vacuum is stopped and the bottle is released by grabbersuction 412. The RDS computer 205 stores the exact position and contentof the container in an inventory database. This process is repeateduntil all product 1204 containers have been removed from the transportcarton 1007 and placed in one of the rotating shelves 602 and theinventory database has been populated. In the event thatnon-prescription medications are to be loaded into inventory, some orall of the product verification steps can be eliminated.

Product Dispensing Verification

Prior to dispensing product 1204 to a user, multiple, independentverifications are performed by the RDS to ensure that the correct typeand quantity of product are dispensed. After a container of product 1204is removed from a rotating shelve 602, robotic arm system 400 moves thecontainer through a series of verification processes. Theseverifications include a barcode scan, verification of the containershape and size by movement past sensors, bitmap photographic recognitionand optical character recognition software, verification of thecontainer weight via an accelerometer or scale, visual verificationthrough direct imaging, and/or receipt of RFID information from theproduct container. The shape of the container and the height of thecontainer may also be verified to ensure that the proper product isbeing dispensed. The RDS software is programmable to require that one orall of these verifications is to be successfully completed before aproduct 1204 is dispensed to a user. This verification process iscritical to ensuring that only the correct product 1204 is dispensed toa user.

Product Dispensing Labeling

Products are received from the repackaging pharmacy 17 with therepackaging pharmacy's label and RFID tag on the product container.After a container of product 1204 has completed the verificationprocess, a patient specific label is printed and applied to thecontainer. The RDS labeling system is comprised of software that resideson the RDS computer 205, a label printer, and a label applicator. In oneembodiment, the label printer and label applicator are positioned in thebase of the vault 100. Robotic arm system 400 moves a container ofproduct to be dispensed into position for labeling to occur. Once theproduct has been labeled a bitmap image of the applied label is recordedand stored in a designated database.

RDS Operation

In one embodiment, a person who desires to obtain prescriptionmedication from an RDS must first complete the PRS registration processand supply the necessary personal, medical, and biometric information.Alternatively, identification can be verified through the use of acredit card or smart card, or other device upon which data can be storedand then read at the RDS. Once registered, such a person may obtain anelectronic prescription from a participating prescription provider. Theelectronic prescription is communicated over a communications network tothe RDS which may be located at the provider's office, at a pharmacy, orat another remote location. Once the prescription is communicated, theprescription is then available to be received at the RDS by the patient.

At the RDS, the patient must first enter his/her personal biometricinformation through biometric reader 114. The RDS then compares thebiometric information entered with the biometric information databasecompiled through the PRS system. Once a patient's identity is verified,the RDS computer system determines the prescription or prescriptionsauthorized to be dispensed to the patient. For each such prescription,the RDS communicates through the PBMS 15 to verify insurance coverageand to determine the amount of co-pay, or other payment, that isrequired. The patient then provides payment information which isverified through the FTS 14, or pays directly through cash receiver 122.Once payment is confirmed, the RDS printer 121 prints a financialreceipt and a prescription information sheet and begins the dispensesequence.

The RDS computer 205 consults the inventory database to determine thestorage location of the product 1204 to be dispensed. Robotic arm system400 then retrieves the product 1204 from the applicable rotating shelve602. The product 1204 is then moved by robotic arm system 400 intoposition for product verification. One or more verifications consistingof barcode scan, RFID tag reading, container shape and size, bitmapimaging and OCR character recognition, container weight are performed.If the selected product 1204 does not match the product prescribed, theproduct 1204 is returned by robotic arm system 400 to transport carton1007 and the RDS computer identifies the next storage location whereappropriate product 1204 is stored.

If the verification process is successfully completely, the product 1204is moved to the product labeling area inside vault 100. There, a patientspecific label, containing, a bar code, the patient's name, prescriptionnumber, and directions for taking the medication is printed and appliedto the product 1204. Once this patient specific label is printed andapplied, a second verification process ensues. This second verificationincludes a bar code scan and the creation of a bitmap image of thelabel. The bitmap image is compared, via OCR software, to the imagestored in the RDS computer for that particular prescription. Uponcompletion of this second verification, product 1204 is moved by roboticarm system 400 to the product dispensing area and dispensed throughdispensing slot 105. Prescription pick-up sensor 105 provides a signalto RDS computer 205 that the prescription has been removed fromdispensing slot 105 and completes the dispensing process. In the eventthat a dispensed product is not removed from dispensing slot 105 withina selectable time frame, the product is automatically retrieved from thedispensing slot and removed from inventory.

In another embodiment, the RDS can also dispense product 1204 topatients that have received a paper prescription instead of anelectronic prescription from the provider. In this embodiment, thepatient, after verifying identity at the RDS, inserts the paperprescription into prescription reader 117. The prescription is scannedand a bitmap image is generated and transferred via the communicationsnetwork to a participating pharmacist. This pharmacist then reads theprescription and converts it into an electronic prescription which iscommunicated back to the RDS. At this point, the dispensing processproceeds as described above.

In yet another embodiment, the RDS can also dispense non-prescriptionproducts to patients that have not previously completed the PRS 10process. In this embodiment, non-prescription products are also stockedin the RDS. These products are available to persons without therequirements that a prescription be first transmitted to the RDS andthat the user supply biometric identification prior to receivingproduct.

1. A high security transport container for moving prescriptionmedications comprising: a. a lockable container; b. means for lockingand unlocking said container; c. a shipping label, said shipping labelhaving a first position wherein a first shipping address is displayedand a second position wherein a second shipping address is displayed; d.means for measuring at least one environmental condition within saidcontainer; e. a memory configured to receive and store said measuredenvironmental condition; and f. means for communicating a content ofsaid memory.
 2. The transport container of claim 6, wherein said lockingand unlocking means are internal to said container.
 3. The transportcontainer of claim 6, further including means for measuring andrecording acceleration.
 4. The transport container of claim 6, whereinsaid shipping label moves from said first position to said secondposition when said transport container is unlocked.
 5. The transportcontainer of claim 6, further including an RFID tag capable oftransmitting a unique serial number.